Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Print max-in-flight value alongside deployment status [v8] #3088

Closed

Conversation

pivotalgeorge
Copy link
Contributor

@pivotalgeorge pivotalgeorge commented Aug 7, 2024

Description of the Change

This prints max-in-flight: <value> after the deployment status, when there is an Active deployment for an app and when max-in-flight is set to a non-default value

Why Is This PR Valuable?

It provides the user with information/confirmation that they have set a non-default max-in-flight value

Applicable Issues/PRs

this PR is based on #3085 and is therefore blocked on that PR getting merged into v8

+@joaopapereira @weresch

joaopapereira and others added 11 commits August 7, 2024 09:40
Signed-off-by: João Pereira <joaod@vmware.com>
Signed-off-by: João Pereira <joaod@vmware.com>
Signed-off-by: João Pereira <joaod@vmware.com>
Signed-off-by: João Pereira <joaod@vmware.com>
Signed-off-by: João Pereira <joaod@vmware.com>
Signed-off-by: João Pereira <joaod@vmware.com>
Signed-off-by: João Pereira <joaod@vmware.com>
Signed-off-by: João Pereira <joaod@vmware.com>
Signed-off-by: João Pereira <joaod@vmware.com>
Co-authored-by: Greg Weresch <greg.weresch@broadcom.com>
…s table

when it is set to non-default value (currently 1)

Co-authored-by: Greg Weresch <greg.weresch@broadcom.com>
@pivotalgeorge
Copy link
Contributor Author

pivotalgeorge commented Aug 7, 2024

remember to rebase on top of v8 once #3085 is in, so integration test fixes are included

@weresch
Copy link
Contributor

weresch commented Aug 12, 2024

PR #3097 supersedes this PR. Since #3085 is now merged into the v8 branch, I realized I couldn’t edit #3088 out of Draft status to move the changes on top of v8. So I created PR #3097 to take the new changes from #3088 and target the v8 branch.

@pivotalgeorge pivotalgeorge marked this pull request as ready for review August 12, 2024 15:54
@pivotalgeorge
Copy link
Contributor Author

closing as this has been replaced by #3097

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants